Havish M Consulting
Customer Case Study · AI Photography QC
Retail × Havish M Consulting

Every product photo checked against the style guide, in seconds

The retailer's studios shoot thousands of product images for e-commerce, and every set must follow strict style guides on sequence, framing, cropping and background. HMC built a dual-tier vision AI pipeline that turns the style guides into JSON rulebooks, filters junk images cheaply, and judges every image set with a clear, explainable QC report.

ClientRetail FunctionE-commerce · Studio Operations ThemeVision AI Image QC
Manual image review time
0% less
▼ QA makes only the final call
Images stopped before the expensive VLM
0%
▼ fewer paid API calls
Average judge confidence
0%
▲ with evidence per rule
Image sets checked on the latest rulebook
0%
▲ same rules in every studio

Figures indicative; validated metrics available on request.

The Challenge

A style guide nobody could check at scale

Studio shoot, manual review against the style guides, then the bottleneck: slow, subjective and error-prone checks before new SKUs could go live.

Thousands of raw images

Every season, every category, from several studios and agencies.

Massive style guides

Sequence, shot types, framing, creases and backgrounds differ by category and season.

Hours of manual QA

QA teams compared each image to the guide by eye, set by set.

Subjective and late

Different reviewers, different answers; reshoots found after the set was struck.

HMC Approach

Rules first, cheap filters next, the VLM last

A pipeline that spends expensive vision AI only where it adds value.

Select a step to see what happened.

Discover · How QA really judges a set

Sat with QA reviewers and photographers.

  • Style guides by category: sequence, shot types and quality standards.
  • Most common rejections: wrong order, model shots instead of flat lays, cropped edges, creases.
  • Where junk images entered the queue.

Deliverable: Rejection taxonomy and pipeline design.

Design · Guidelines as JSON

A machine-readable rulebook per category.

  • Required sequence with shot type and notes per position.
  • Quality standards: first image, negative space, creases, cropping, background.
  • Tiered pipeline so cheap checks run before the VLM.

Deliverable: Rulebook schema and rule registry.

Build · Scraper, router, gatekeepers, judge

End to end in one app.

  • Guideline scraper and VLM that writes the JSON rulebook.
  • Router matching each SKU to its rulebook; Tier 0, 1 and 1.5 gatekeepers.
  • Tier 2 VLM judge with per-rule scores, evidence and crop coordinates.

Deliverable: Working QC pipeline.

Adopt · Photographers see it first

Feedback before the set is struck.

  • Instant, explainable result per image set.
  • QA managers review the aggregated report and make the final call.
  • Rulebooks marked "AI draft" until the retailer reviews them.

Deliverable: Pilot results and studio SOP.

Scale · Every category and studio

Global alignment across studios.

  • Rule registry for all categories, versioned by season.
  • Agency submissions checked on upload.
  • QC report feeds the catalogue go-live process.

Deliverable: Roll-out plan.

The Solution

Run the QC pipeline

Turn a style guide into rules, push a batch through the gatekeepers, and judge image sets. Rearrange or break the images and watch the verdict change. Product images here are drawn illustrations; with an OpenAI key you can judge your own photos.

✦ Use a live vision model

Optional. Without a key, rulebooks come from the registry and the judge applies the rules to the sample sets. Add your OpenAI key to extract a rulebook from a style-guide screenshot and to judge your own product photos.

Rules engine
Your key and images go only from this browser to OpenAI.
01 · Rule registry

From style guide to JSON rulebook

Each category's visual style guide is read and turned into a strict, machine-readable rulebook: the required image sequence and the quality standards. Pick a category, then extract.

Rules engine

JSON rulebook

02 · Routing & Tier 1 gatekeepers

Stop junk before it reaches the VLM

A batch of 50 SKUs arrives from the studio and an agency. The router matches each SKU to its rulebook; cheap gatekeepers check that each image decodes, meets resolution and file size, and actually shows the right garment. Only clean image sets go to the Tier 2 judge.

Stopped at this tierEach tile is one image

Gatekeeper logs

Run the batch to see the logs.

Synthetic batch; garment images are illustrations. Thresholds: 2000 × 2667 px minimum, 3 MB maximum, apparel classifier confidence 0.80.

03 · Tier 2 VLM judge

Judge an image set against its rulebook

Pick a submitted set. Drag images to reorder, or use the menu under each image to break it (crop an edge, add creases, swap in a model shot). The judge re-checks sequence, shot type, cropping, creases, negative space and background, with evidence and crop coordinates.

Rules engine

Submitted sets

Rulebook

Submitted images, in order

Rulebooks marked "AI draft" are not reviewed by the retailer; for demonstration only.

04 · Final QC report

What to reshoot, before the set is struck

The batch rolls up into one report: pass rate, the rules that fail most, and a reshoot list by studio. QA managers review it and make the final call; photographers get a plain note on what to fix.

Rules engine

Failing rules

Reshoot list

SKUCategoryStudioFailed rules
Impact Dashboard

Less review, more SKUs live

QA hours per thousand images fell by about 90%, and the studio clears far more SKUs a day for the site.

QA hours per 1,000 images

Donut: where the review time goes

SKUs cleared for the site, per day

Spiral heatmap: one ring per week, one cell per day, week 1 at the centre

Figures indicative; validated metrics available on request.

Before vs After

How product images are checked now

DimensionBeforeAfter
Style guidesPDFs and screenshots, shared by handScraped and turned into JSON rulebooks
Junk imagesReviewed like everything elseStopped by cheap gatekeepers
Checking a setBy eye, against the guideVLM judge, rule by rule, with evidence
ConsistencyDepends on the reviewerSame rules, every studio, every time
FeedbackAfter the set is struckInstant, while the photographer is on set
QA effortHours per batchReview the report, make the final call
Tools & Tech Used

The QC pipeline stack

Azure OpenAI GPT-4.1 mini vision judge and rule extraction Guideline scraper style guides from the internal ecosystem JSON rule registry versioned rulebooks by category ML classifiers Tier 1.5 junk and category checks Python image checks decode, resolution, file size QC web app photographer and QA views
Key Takeaways

What any e-commerce studio can borrow

01

Turn the guide into data first

A JSON rulebook is something every studio, agency and model can follow the same way.

02

Filter cheaply, judge carefully

Basic checks and small classifiers stop junk for a fraction of the cost of a vision model.

03

Explain every verdict

A score, an observation and the exact image and crop make the AI's call easy to trust and to act on.